Use this file to discover all available pages before exploring further.
You’re a product person at a small team. You’ve done maybe 1-2 user interviews, but the insights live in scattered notes that nobody looks at. You want to understand what customers actually need, but analyzing conversations manually takes hours you don’t have.This guide shows you how to record 5 customer calls and get real insights in 30 minutes—not 30 hours.
Connect your calendar so BuildBetter automatically joins your customer calls.[screenshot: Settings > Integrations page showing Google Calendar and Outlook options]
1
Connect Your Calendar
Go to Settings → Integrations
Click Connect next to Google Calendar or Outlook
Authorize BuildBetter to read your calendar
[screenshot: Calendar connection success screen]
2
Set Up Recording Rules
Go to Settings → Organization → Bot Recording Rules
Click Create Rule
Set filter: “Event title contains” → type “customer” or “user interview”
Save rule
[screenshot: Bot recording rules configuration showing a rule for “customer” in title]
This tells BuildBetter to only join calls with “customer” or “user interview” in the title. It won’t join your internal standups.
3
Verify Upcoming Calls
Go to Home page
Check Upcoming Calls section
Confirm your customer calls appear in the list
[screenshot: Home page with upcoming calls widget showing 3 scheduled customer interviews]That’s it! BuildBetter will auto-join these calls.
After your first call is processed, let’s see what BuildBetter found.[screenshot: Calls & Recordings page showing a processed call with transcript and signals]
1
Open a Processed Call
Go to Calls & Recordings
Click on your first customer call
You’ll see the full transcript with timestamps
[screenshot: Call detail page showing transcript on left, summary on right]
2
Review Auto-Extracted Signals
Scroll down to the Signals section on the call page.[screenshot: Signals section showing 8 signals extracted from a call, with types like “Problem”, “Feature Request”, “Question”]Each signal shows:
Type: Problem, Feature Request, Question, Praise, etc.
Summary: What the customer said (in their words)
Sentiment: How they felt about it (😊 positive, 😐 neutral, 😣 negative)
Severity: How urgent (🟢 minor, 🟡 important, 🔴 critical)
Quote: Exact customer quote with timestamp link
Click the timestamp on any signal to jump to that exact moment in the recording.
3
Understand Signal Types
BuildBetter automatically categorizes feedback:
💡 Feature Request: “I wish I could…”
🐛 Problem/Bug: “This doesn’t work…”
😤 Complaint: “I’m frustrated by…”
🎉 Praise: “I love that…”
❓ Question: “How do I…”
🎯 Need: “What I’m trying to do is…”
No tagging needed—it’s automatic.
After 2-3 calls, you’ll start seeing patterns. Let’s find them.
Now you have 3-5 calls recorded. Time to find what customers are really telling you.
1
Go to Signals Page
Click Signals in the left navigation[screenshot: Signals page showing all signals from multiple calls in a list view]You’ll see ALL signals from ALL your calls in one place.
2
Filter for Problems
Use the filter to focus on customer problems:
Click Filter button
Under Signal Type, select Problem
Click Apply
[screenshot: Signals filter panel with “Problem” type selected]Now you see ONLY problems customers mentioned across all 5 calls.
3
Sort by Common Themes
Look for patterns:Example: You might see:
“Onboarding is confusing” (mentioned in 4/5 calls)
“Export doesn’t work” (mentioned in 3/5 calls)
“Need mobile app” (mentioned in 2/5 calls)
If 3+ customers mention the same thing unprompted, it’s a real pattern—not a one-off request.
4
Try Natural Language Search
BuildBetter understands plain English. Try:Type in the search: “pricing concerns”[screenshot: Search bar with “pricing concerns” typed, showing filtered results]It finds all signals related to pricing, even if customers used different words like “cost”, “too expensive”, “budget”, etc.
Key Insight: You’ve just done in 10 minutes what used to take 5 hours of manual note review.
Click Clustering in the left navigation[screenshot: Clustering page showing signal analytics workspace]This is BuildBetter’s visualization workspace.
2
Create a Simple Dashboard
Click Customize Dashboard (top right)
You’ll enter edit mode
[screenshot: Dashboard in edit mode with “Add Card” options]
3
Add 'Top Problems' Chart
Click Add Card
Select Bar Chart
Configure:
Data Source: Signals
Filter: Signal Type = “Problem”
Group By: Topic/Theme
Title: “Top Customer Problems”
Click Add
[screenshot: Bar chart configuration panel]You’ll see a chart showing which problems were mentioned most.[screenshot: Bar chart showing “Top Customer Problems” with bars for different issues]
4
Add 'Feature Requests' Chart
Repeat for feature requests:
Add another Bar Chart
Filter: Signal Type = “Feature Request”
Title: “Most Requested Features”
[screenshot: Dashboard with 2 charts - Problems and Feature Requests side by side]
5
Save & Share
Click Save Dashboard
Copy the URL from your browser
Share link with your team in Slack
Anyone in your workspace can view this dashboard. It updates in real-time as you add more calls.
Now you have: A live, visual dashboard that updates automatically as you do more interviews.
BuildBetter’s AI can answer questions about your calls instantly.
1
Open Chat
Click Chat in the left navigation[screenshot: Chat interface with empty conversation]
2
Ask Your First Question
Try this: “What are the top 3 customer problems based on my recent calls?”[screenshot: Chat response showing AI-generated list of top 3 problems with quotes and citations]The AI will:
Analyze all your calls
Identify the most-mentioned problems
Show you exact customer quotes
Cite which calls they came from
3
Follow Up Questions
Keep asking:
“What should I build first?”
“Which customers mentioned onboarding issues?”
“Are there any quick wins I could fix?”
[screenshot: Multi-turn conversation in Chat showing follow-up questions and answers]
4
Generate a Summary Document
After the AI responds, click Generate button
Select Generate Document
Choose template: “User Research Summary”
Click Generate
[screenshot: Generate document dropdown with template options]You’ll get a formatted document you can share with your team or stakeholders.[screenshot: Generated document showing “User Research Summary - Week 1”]
Key insight discovered: 4/5 users mentioned the same onboarding problem in different ways. Sarah’s team fixed it the next sprint. NPS went up 12 points.
Always ask for consent! Say: “I’d like to record this so I can focus on our conversation instead of taking notes. Is that okay?”Most customers say yes. If not, use BuildBetter’s upload feature to transcribe your notes after.
How accurate is the transcription?
95%+ accuracy for clear audio. BuildBetter handles accents, background noise, and multiple speakers well.You can edit transcripts if needed, but most teams find them accurate enough as-is.
What if I don't have 5 calls yet?
Start with 2-3! You’ll still get value. The more calls you add, the better the pattern detection becomes.You can also upload old recordings or notes to bootstrap your data.
How do I know which problems to prioritize?
Look for:
Frequency: Mentioned by 3+ customers
Severity: Marked as 🔴 critical or 🟡 important
Sentiment: Strong negative emotion (😣)
Segment: Problems from your ideal customers
Chat can help: “Which problems should I prioritize?”
Can I delete calls if I recorded the wrong meeting?
Yes! Go to Calls & Recordings, click the call, and click Delete. It’s removed permanently.
You’re now equipped to turn customer conversations into insights in minutes, not hours. Record your next 5 calls and see the difference data-driven decisions make.
Remember: The goal isn’t perfect data—it’s to make better decisions faster. Start simple, record calls, find patterns, and iterate.